New Star Software Collection/NSS_Collection.iso/3-069 qemm 603/1.ima/QEMM-MAN/CH2.QEM

Text File | 1991-10-07 | 13.4 KB | 308 lines

Chapter 2

Installation QEMM

 You install QEMM-386 by running the QEMM installation program,
INSTALL. You should also use INSTALL if you are installing an
upgrade of QEMM-386.

 If you have a new 80386 PC, be sure to complete the standard
installation and setup procedures of your PC before installing
QEMM-386.

 QEMM-386 is a device driver, which means that it must be loaded
as part of the boot sequence of your PC. INSTALL automatically
creates the necessary command to load QEMM-386 and places it at
the beginning of your CONFIG.SYS file~dash~or creates a
CONFIG.SYS file if you don't have one already.

 INSTALL also installs Quarterdeck Manifest, Quarterdeck's
comprehensive memory reporting and analysis program, if Manifest
is bundled together with QEMM-386. Manifest describes your PC,
specifically the software and hardware that use your memory. In
doing so, it gives you an understanding of how best to use your
PC's memory.

 As a precaution, before installing QEMM-386, you should check
that there is no other expanded memory manager loaded in your
CONFIG.SYS. An expanded memory manager characteristically has the
letters, EMM in its name, such as EMM386.SYS which is provided by
Microsoft with Windows 3.0. Windows 3.0 users should review the
Section Installing QEMM-386 with Windows 3.0 before proceeding.

 Also, if Microsoft's HIMEM.SYS extended memory manager is
specified in your CONFIG.SYS file, you should remove it. QEMM-386
is an extended memory manager, and provides the same
functionality as HIMEM.

~Subhead~ Installing QEMM-386

 To install QEMM-386:

~Step~ Place the QEMM-386 diskette in drive A.

~Step~ Type A:INSTALL and press <Enter>.

NOTE: If you have an LCD or Gas Plasma display, as on some
laptops, we recommend that you run INSTALL in monochrome mode.

~Step~ Type A:INSTALL /m and press <Enter>.

Follow the instructions on the screen. INSTALL copies the QEMM
files to your hard disk and allows you to configure QEMM.
INSTALL's base configuration settings, for most of you, will be
correct.

The most common reason that you will want to change QEMM-386's
settings is when you're using VDISK. Normally, QEMM-386 takes all
of extended memory for itself. If you are using VDISK, you'll
want to allocate part of extended memory to VDISK, using QEMM's
EXTMEM command line parameter. For information on the EXTMEM
parameter, see Chapter 3: The QEMM386.SYS Program, page 19.

INSTALL displays a separate screen for each instruction you are
likely to want to change. For information about the QEMM's
command line parameters, see Chapter 3 The QEMM386.SYS Program,
page 13.

That's all there is to installing QEMM-386. Since QEMM-386 is a
device driver, you do have to reboot your system for its settings
to take effect. Most likely, your memory has been configured by
INSTALL in the following way:

~Item~ All the memory in your PC has been made into expanded
memory, compatible with the EMS 4 expanded memory specification.

~Item~ If you are installing an upgrade to QEMM-386, the install
program honors the way you have previously configured your
memory.

To see how your memory is used, refer to Memory Report in Chapter
4, The QEMM.COM Program on page 33. To see a map of your first
megabyte of memory, see Chapter 4 The QEMM.COM Program, Type
Report, page 30.

Also, if you are unfamiliar with memory, please refer to
Quarterdeck's Manifest program. Manifest explains memory (first
meg, expanded, extended). It describes the various expanded
memory specifications. It also gives you information about your
DOS configuration and the hardware in your PC. Manifest displays
the same information, in its category QEMM-386, as does
QEMM.COM~dash~but in a more pleasing visual format and with
access to other related information.

The last screen displayed by the QEMM-386 installation program is
a screen that tells you to reboot your PC to load QEMM-386, and
recommends that you then run the Optimize program. Optimize loads
your TSRs, device drivers, and DOS resources in high memory. By
loading these in high memory, you have more memory below 640K
available for programs.

Optimize does two things:

~Item~ First it modifies the QEMM386.SYS command line~dash~adding
the RAM parameter. This parameter maps memory into any available
memory addresses in the high memory addresses between 640K and
1024K. We call the memory mapped into these available addresses,
high RAM. High RAM is memory ready to be used to load TSRs,
drivers (such as networks), and DOS resources~dash~thus freeing
memory below 640K and giving your DOS programs more memory in
which to run.

~Item~ Then it looks at your CONFIG.SYS and AUTOEXEC.BAT files to
determine what can be loaded in high RAM using QEMM-386's LOADHI,
and DOS resources programs. It then changes your CONFIG.SYS and
AUTOEXEX.BAT files accordingly.

If you are not using large DOS programs and hence are not
suffering from RAM cram, you will not need to run Optimize. Also
if you are a sophisticated user, you may wish to choose what is
loaded high. In this case, please refer to Chapter 5, The LOADHI
Programs, and Chapter 6, DOS Resource Programs.

After rebooting, your PC is ready to run expanded memory
programs. NOTE: the QEMM-386 program, VIDRAM, discussed in
Chapter 7 The VIDRAM Program, can make 96K more memory available
to your DOS program~dash~if you don't need to use EGA or VGA
graphics.

If after rebooting, your system fails to initialize, you can
recover without having to resort to a boot floppy by doing the
following:

~Step~ Reset your system again. Use the power switch if
necessary.

~Step~ Wait until you hear a beep, then hold down the Alt key.

    QEMM pauses with the message, "QEMM; Press any key to
continue. Esc to abort."

~Step~ Press the Esc key.

Your system will then proceed with the boot sequence. QEMM will
not be loaded and thus, no programs will be loaded into high RAM.
Your system will, however, be usable. Refer to Chapter 3, The
QEMM386.SYS Program parameters for changes needed on your system.
See also Appendix A Troubleshooting for additional guidelines.

~Subhead~ Optimizing Your Memory

 The Optimize program scans your CONFIG.SYS and AUTOEXEC.BAT
files to find device drivers, TSRs, and DOS resources that can be
put in the high memory area. From its analysis, Optimize makes
the changes to these files to make use of this memory for you. It
also makes sure you have a memory manager installed that can turn
the high memory area into high RAM.

For many, the use of Optimize during installation is all that is
necessary to make immediate use of the high memory area. To run
Optimize:

~Step~ Change to the QEMM-386 subdirectory you specified during
installation.

~Step~ Type Optimize and press <Enter>.

In special situations, some of you will want to customize your
system further. The reference sections in this manual are for
that purpose. In particular, see the Chapter 5 The LOADHI
Programs, and Chapter 6 The DOS Resource Programs. In either
case, we recommend that you run Optimize now. The changes you
will see in your start-up files will help you use these programs.

If you choose not to run Optimize now, you can run it at any time
in the future. In fact, you should run Optimize whenever you add
device drivers, TSRs, change your DOS resources memory or change
your high memory configuration in any way.

Optimize changes CONFIG.SYS and AUTOEXEC.BAT. Your original files
are first copied to CONFIG.QDK and AUTOEXEC.QDK. Optimize also
re-boots your system twice before it is done. When it completes,
your system should have programs and data in high RAM. And, your
application programs should have more memory available to them.

NOTE: If your AUTOEXEC.BAT file runs a program that is not a TSR
and does not exit immediately on its own, then you will have to
quit that program manually to allow Optimize to continue.

Optimize does not attempt to read or analyze any batch files it
finds within your AUTOEXEC.BAT. Any TSRs loaded from within an
embedded batch file will not be loaded into high RAM. If at all
possible, consider putting the contents of these batch files
directly into AUTOEXEC.BAT. Then re-run Optimize to gain even
more memory.

~Subhead~ Running Optimize After Installation

 To run Optimize at any time in the future, change to the
subdirectory that your used to install QEMM-386 and

~Step~ Type Optimize and press <Enter>.

Optimize changes CONFIG.SYS and AUTOEXEC.BAT. Your original files
are first copied to CONFIG.QDK and AUTOEXEC.QDK. Optimize also
re-boots your system twice before it is done. When it completes,
your system should have programs and data in high RAM. And, your
application programs should have more memory available to them.

~Subhead~ Installing QEMM-386 With Windows 3.0

 There are several considerations with respect to running
QEMM-386 v5.1 and Windows 3.0 together.

~Item~ Use of the QEMM-386 "RAM" parameter.  This parameter will
automatically be installed when you run the OPTIMIZE program, or
if you answer "Yes" to the question "Fill All High Memory with
RAM?" during the QEMM-386 Install procedure.


 QEMM-386 by default provides memory management in the monochrome
video area (B000-B7FF), when it is not in use by a video adapter.
If you use the RAM parameter, QEMM-386 fills these addresses with
RAM so that resident programs, drivers and some of DOS overhead
can be loaded into high memory.  However, if you don't use the
RAM parameter, Windows 3.0 seems to become confused by QEMM-386's
memory management in this area and may refuse to start up in 386
enhanced mode.

 If you will be running Windows 3.0 and for some reason don't
want to use the RAM parameter, you should exclude QEMM-386's use
of this area by using, X=B000-B7FF as a parameter to the
QEMM386.SYS driver.

~Item~ If you install Windows 3.0 after installing QEMM-386,
Windows Setup inserts the driver HIMEM.SYS before the QEMM386.SYS
driver. When QEMM-386 loads, it can allocate all of the memory
that is controlled by the HIMEM.SYS driver, so the presence of
HIMEM.SYS is not a big problem.

 However HIMEM.SYS takes 2.8K of conventional memory which
QEMM-386 cannot reclaim. Since QEMM-386 provides all the features
of HIMEM.SYS, you may want to avoid loading HIMEM.SYS altogether.
You can do this by selecting "Let you review & edit changes
before modifications are made" from Windows Setup when you get to
the menu which offers this option. Just edit out the line which
contains the HIMEM.SYS driver from the "Proposed CONFIG.SYS
file." Or, you can remove the line from your CONFIG.SYS file at a
later time using a text editor.

~Item~ If Windows 3.0 is already installed when you install
QEMM-386, Windows Setup installed a driver called HIMEM.SYS. The
QEMM-386 installation procedure puts the QEMM386.SYS driver
before the HIMEM.SYS driver. When the system boots, the HIMEM.SYS
driver sees that an extended memory manager (QEMM-386) is already
installed and does not load itself.

 This is fine since the QEMM386.SYS driver provides all the
features of HIMEM.SYS. Also, since HIMEM.SYS fails to load, it
will not be taking any memory. However, it will beep and produce
a message, saying "Error: An Extended Memory Manager is already
installed." To get rid of this error message, remove the line
which loads the HIMEM.SYS driver from your CONFIG.SYS file using
a text editor.

~Item~ Use of Microsoft's SMARTDRV.SYS. The Windows Setup
procedure installs Microsoft's disk cache called SMARTDRV.SYS.
The default size of this cache tends to be large. Windows can
reclaim memory from this cache when it starts up, however
programs that are run outside of Windows which use expanded
memory cannot do this. If you run programs outside of Windows
which would benefit from expanded memory, you may want to
consider either removing SMARTDRV.SYS entirely from your
CONFIG.SYS file, or at least reducing its size.


 SMARTDRV.SYS takes parameters to set the size of the cache, the
first parameter being the "NormalCacheSize" and the second being
the "MinimumCacheSize". An example SMARTDrive installation might
look as follows:

 DEVICE=C:\WINDOWS\SMARTDRV.SYS 1024 256

 In this example, SMARTDrive takes 1024K (1MB) of memory when you
are not in Windows and 256K while you are running Windows. While
it is difficult to suggest a cache size that might be best for
you, one possible suggestion might be to use the minimum amount
only. To do this, using the example above, you would edit the
line to read:

 DEVICE=C:\WINDOWS\SMARTDRV.SYS 256  256

 If you are not running programs that are disk intensive,
deleting the cache entirely may make sense. Further information
on the parameters used to control the size of SMARTDRV.SYS can be
found in the back of the Windows 3.0 manual.

~Item~ EMS and VCPI support in Windows 3.0 Standard Mode. When
Windows is started in standard mode, it allocates all of the
memory controlled by QEMM for its own operation and for use by
Windows specific applications. Non-Windows applications, started
in Windows, which might otherwise be able to use some of
QEMM-386's memory using the Expanded Memory Specification (EMS)
or Virtual Control Program Interface (VCPI) will not be able to
find any, since all memory is at that point under the control of
Windows. If you have such programs, you can reserve some
additional memory for them by using the EMBMEM parameter
documented in Chapter 3, The QEMM386.SYS Program.